
APAR= II09778
OS/2 WARP V4 (MERLIN) COMPATIBILITY


** Last updated 3/28/97 **

This Informational APAR contains information regarding
installing and using Client Access/400 Optimized for OS/2 V3R1M1
on IBM OS/2 Warp Version 4 (Merlin).  The OS/2 optimized V3R1M1
client is supported running on OS/2 Warp Version 4 with the
following limitations:

    -  If you are installing the Optimized client on OS/2 Warp
       Version 4, you must apply a PTF prior to installing the
       client.  Either apply PTF SF37615 or ftp the latest
       fix and follow the instructions in the cover letter.
       See the Installation Problem section below for more
       information. Note: This fix only applies to new
       installations of Client Access/400 Optimized on OS/2
       Warp Version 4.  These fixes are not required if you
       already have Client Access installed and are upgrading
       to OS/2 Warp Version 4.

    -  You cannot run PCOM Entry (5250 emulation) that
       is supplied with Warp Version 4 and Client Access PC5250
       on the same PC.  See Installing the PC5250 Component
       of Client Access/400 section below for more
       information.

    -  The Client Management functions, such as SNMP and Problem
       Log do not work.  We are working to resolve the problems
       and we will update this information APAR as more
       information becomes available.

    -  On some PCs the VPD.INI file may be corrupted which will
       prevent Client Access from installing.  See the VPD.INI
       File Corruption section in Informational APAR II09210
       for recovery instructions.

    -  Make sure to read the following Informational APARs for
       additional information regarding Client Access that is
       not specific to OS/2 Warp Version 4:
         II09210 - Installation Information
         II09213 - Known problems

    -  Client Access/400 Optimized for OS/2 V3R1M0 is not
       supported on OS/2 Warp Version 4.  You must use V3R1M1
       which provides additional function than V3R1M0. The
       V3R1M1 client code is available at no additional
       charge.

    -  Testing has not yet been completed for Ultimedia on
       OS/2 Warp Version 4.

    - Client Access/400 Optimized for OS/2 has not been tested
      and is not supported on the DBCS GBK version of OS/2
      Warp Version 4.0.


Installation Problems
_____________________

OS/2 Warp Version 4 ships several functions that replace
Client Access/400 functions.  Among these functions are the
Systems Management Client which replaces the System
Information Agent shipped with Client Access and the Desktop
Management Interface (DMI).  The Client Access installation
program does not correctly detect the presence of these
two functions.

If you selected to install the Systems Management Client when
you installed OS/2 Warp Version 4, then the installation
program for the OS/2 Optimized client will not complete
successfully.

If you did not select to install the System Management Client
when you installed OS/2 Warp V4, then the Client Access/400
installation will complete successfully.  However, the
installation program will install the DMI version from Client
Access which corrupts the DMI database shipped with Warp V4.

A fix is available by applying PTF SF37615 or from the
IBM FTP Software site:

  ftp.software.ibm.com

in the following directory:

  as400/products/clientaccess/os2opt/v3r1m1/ptfs/sf37615

The fix can also be downloaded from our homepage:

   http://www.as400.ibm.com/client/caos32b.htm

The file is a self-extracting zip file called
sf37615.exe.  Make sure to follow the instructions in the
readme file and the PTF cover letter. This fix correctly
detects OS/2 Warp Version 4 and does not install the
Client Access version of the System Management Client nor
does it install DMI. If you want the System Management
functions you must install the version that ships with OS/2
Warp Version 4.  DMI is installed by default when you install
OS/2.


Installing the PC5250 Component of Client Access/400
____________________________________________________

If you intend to install the PC5250 component of Client Access,
you must delete any PCOM Entry session objects that you have
created.  The existence of these objects will prevent the Client
Access PC5250 component from installing.  If you decide to
remove PC5250, the Personal Communication folder from PCOM
Entry will also be removed.  To recover this folder, run the
INSTALL.EXE program that is in the TCPIPPCOMOS2 directory.
This will recreate the Personal Communications folder on the
desktop.


